Method and system for managing coronavirus screening operations

ABSTRACT

A method may include determining whether to perform a coronavirus diagnostic test on a member of a predetermined population. The method may further include sending, in response to determining that the coronavirus diagnostic test should be performed on the member, a coronavirus testing kit to the member. The coronavirus testing kit may include a return shipping container, a substrate, and a specimen transport container configured to store a biological specimen. The method may further includes determining whether the biological specimen is received at a laboratory facility from the member. The method may further include transmitting, to at least one user device associated with the member, a notification regarding a coronavirus infection diagnosis based on the biological specimen.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application Ser. No. 63/112,940, which was filed on Nov. 12, 2020, and is incorporated herein by reference.

BACKGROUND

In early 2020, after a December 2019 outbreak in China, the World Health Organization identified SARS-CoV-2 as a new type of coronavirus. The outbreak quickly spread around the world. COVID-19 is a disease caused by SARS-CoV-2 that can trigger what doctors call a respiratory tract infection. An infection by SARS-CoV-2 or its variants may affect your upper respiratory tract (e.g., sinuses, nose, and throat) or lower respiratory tract (e.g., windpipe and lungs). Thus, a coronavirus may spread through person-to-person contact, where infections can range from mild to deadly.

SUMMARY

This summary is provided to introduce a selection of concepts that are further described below in the detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in limiting the scope of the claimed subject matter.

In general, in one aspect, embodiments relate to a method that includes determining, by a server, whether to perform a coronavirus diagnostic test on a member of a predetermined population. The method further includes sending, by the server in response to determining that the coronavirus diagnostic test should be performed on the member, a coronavirus testing kit to the member. The coronavirus testing kit includes a return shipping container, a substrate including an identification code, and a specimen transport container configured to store a biological specimen. The identification code causes a user device to describe a performance of the coronavirus diagnostic test to acquire the biological specimen in response to being scanned by the user device. The method further includes determining, by the server, whether the biological specimen is received at a laboratory facility from the member. The method further includes transmitting, by the server and to at least one user device associated with the member, a notification regarding a coronavirus infection diagnosis based on the biological specimen in response to the biological specimen being received at the laboratory facility.

In general, in one aspect, embodiments relate to a system that includes various user devices coupled to a network. Each user device may be associated with a respective member of a predetermined population. The system further includes a contact management server coupled to the network. The contact management server determines whether to perform a coronavirus diagnostic test on a member of the predetermined population. The contact management server sends, in response to determining that the coronavirus diagnostic test should be performed on the member, a coronavirus testing kit to the member. The coronavirus testing kit includes a return shipping container, a substrate comprising an identification code, and a specimen transport container configured to store a biological specimen. The identification code causes a user device among the user devices to describe a performance of the coronavirus diagnostic test to acquire the biological specimen in response to being scanned by the user device. The contact management server determines whether the biological specimen is received at a laboratory facility from the member. The contact management server transmits, to at least one user device among the user devices, a notification regarding a coronavirus infection diagnosis based on the biological specimen in response to the biological specimen being received at the laboratory facility.

In general, in one aspect, embodiments relate to an apparatus that includes a substrate including an identification code and a specimen transport container that stores a biological specimen. The apparatus further includes a package container addressed to a member of a predetermined population. The package container includes a reply shipping container addressed to a laboratory facility and that stores the specimen transport container after a biological specimen is placed into the specimen transport container. The reply shipping container includes a tracking label associated with the member of the predetermined population. The tracking label notifies a server that the biological specimen is received by the laboratory facility. The identification code causes a user device to describe a performance of a coronavirus diagnostic test to acquire the biological specimen in response to being scanned by the user device.

Other aspects and advantages of the claimed subject matter will be apparent from the following description and the appended claims.

BRIEF DESCRIPTION OF DRAWINGS

Specific embodiments of the disclosed technology will now be described in detail with reference to the accompanying figures. Like elements in the various figures are denoted by like reference numerals for consistency.

FIG. 1 shows a flowchart in accordance with one or more embodiments.

FIG. 2 shows a block diagram of a system in accordance with one or more embodiments.

FIGS. 3 and 4 show flowcharts in accordance with one or more embodiments.

FIGS. 5A and 5B show a computing system in accordance with one or more embodiments.

FIGS. 6A and 6B show schematic diagrams in accordance with one or more embodiments.

FIG. 7 shows an example in accordance with one or more embodiments.

DETAILED DESCRIPTION

Specific embodiments of the disclosure will now be described in detail with reference to the accompanying figures. Like elements in the various figures are denoted by like reference numerals for consistency.

In the following detailed description of embodiments of the disclosure, numerous specific details are set forth in order to provide a more thorough understanding of the disclosure. However, it will be apparent to one of ordinary skill in the art that the disclosure may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description.

Throughout the application, ordinal numbers (e.g., first, second, third, etc.) may be used as an adjective for an element (i.e., any noun in the application). The use of ordinal numbers is not to imply or create any particular ordering of the elements nor to limit any element to being only a single element unless expressly disclosed, such as using the terms “before”, “after”, “single”, and other such terminology. Rather, the use of ordinal numbers is to distinguish between the elements. By way of an example, a first element is distinct from a second element, and the first element may encompass more than one element and succeed (or precede) the second element in an ordering of elements.

In some embodiments, methods and systems of the disclosure provide a fulfillment process and/or tracking process that may be used for detecting coronavirus infections and/or managing testing protocols within one or more populations. In particular, a coronavirus testing kit may be provided to members of a particular population for sample collection of biological specimens. These biological specimens may be returned to a laboratory facility or other testing facility using a return shipping package for performance of a coronavirus diagnostic test. For example, a coronavirus diagnostic test may include a polymerase chain reaction (PCR) test, quantitative polymerase chain reaction (qPCR) test, a reverse transcription PCR (RT-PCR) test, or a reverse transcription quantitative PCR (RT-qPCR) test. Subsequently, the coronavirus diagnostic test may be performed on the biological specimen to determine whether the member is positive (i.e., experiencing biological indicators of an infection) or negative (i.e., without any indication of coronavirus RNA or antigens being in the member's system) for a coronavirus infection.

With respect to saliva coronavirus testing, a user may provide a biological specimen by spitting several times into a funnel attached to a tube. For example, a user may spend several minutes to produce enough saliva to fill the biological specimen container. After attaching a cap to the specimen transport container, the biological specimen may be placed in a return shipping container (e.g., a prepaid postage envelope or other packing container) for delivery to a laboratory facility. In some embodiments, the biological specimen container is a specialized tube that includes one or more stabilization buffers to stabilize the RNA of SARS-CoV-2 and/or one or more inactivation buffers to inactivate the coronavirus. In some embodiments, a saliva sample is stored without RNA stabilization and using sterile, nuclease-free plastic containers as the specimen transport container. Saliva tests may be more comfortable than nasal swabs, but may prove a difficult challenge for users with low saliva productions (e.g., young children). Saliva testing may also provide several other benefits for managing members of a population, such as being non-invasive, preventing exposure of healthy persons to infected patients, and reducing waiting times at testing clinics. Likewise, SARS-CoV-2 may be stable at room temperature. Accordingly, a saliva sample may be collected at 30° C. thereby allowing for accessible collection and transport strategies without the need for expensive cooling operations of the biological specimen.

In some embodiments, a member of a population provides a nasal swab, such as a nasopharyngeal swab specimen, as the biological specimen. A flexible, mini-tip swab may obtain a biological specimen by passing the nasal swab through a member's nostril until the posterior nasopharynx is reached, then left in place for several seconds to absorb secretions, and finally removed while rotating the swab. The nasal swab may be placed in a viral transport medium (e.g., a container inside a specimen transport container) and sealed securely, such as in one or more embodiments described below in the section for Transportation Devices and Systems for Medical Screening Assays.

Turning to FIG. 1, FIG. 1 shows a flowchart in accordance with one or more embodiments. Specifically, FIG. 1 describes a general method for managing one or more coronavirus diagnostic tests for one or more members of a population. One or more blocks in FIG. 1 may be performed by one or more components (e.g., contact management server (240)) as described in FIGS. 2, 5A, 5B, 6A, 6B, and 7. While the various blocks in FIG. 1 are presented and described sequentially, one of ordinary skill in the art will appreciate that some or all of the blocks may be executed in different orders, may be combined or omitted, and some or all of the blocks may be executed in parallel. Furthermore, the blocks may be performed actively or passively.

In Block 100, a determination is made whether to perform a coronavirus diagnostic test on one or more members of a predetermined population based on a predetermined criterion in accordance with one or more embodiments. For example, members may be assigned periodic or random coronavirus diagnostic tests. In some embodiments, a server may analyze current or potential coronavirus infections within a population to determine one or more members at a predetermined risk level for a coronavirus infection. For example, if a member is identified as having a coronavirus infection, the server may identify any members of the population that may have had contact with the infected member (e.g., based on proximity to worker locations, being located on a similar team or department, working with similar equipment, a threshold amount of contact, etc.). In another example, a member may be assigned a coronavirus diagnostic test in response to one or more members testing positive with a coronavirus infection. Likewise, members may be assigned coronavirus diagnostic tests based on other predetermined criteria, such as having preexisting health conditions, the member's age, or other indicators of potential severe Covid-19 symptoms. The server may be similar to a computer system (500) describes below in FIGS. 5A and 5B, and the accompanying description.

Furthermore, a member may be a user who is part of a population where a contact management server controls and administers various communications with the population. Examples of populations may include members of a health plan within a geographical area, employees at a particular company or department within a company, and other groups. In some embodiments, members in a population are adjusted overtime, e.g., new members are added and previous members may be removed.

In some embodiments, a server determines whether to perform one or more coronavirus diagnostic tests on one or more members based on member vaccination data. For example, an unvaccinated member may receive periodic coronavirus diagnostic tests. On the other hand, vaccinated members of a population may be assigned a lower frequency of coronavirus diagnostic tests.

In Block 110, a coronavirus testing kit is sent to one or more members in accordance with one or more embodiments. For example, a contact management server may communicate with an electronic health record (EHR) portal server to obtain contact information (e.g., household address information, personal phone number, full name, etc.) regarding a member assigned a coronavirus diagnostic test. Using the member's contact information, the contact management server may trigger a deliver (e.g., using a network request) a coronavirus testing kit to the member's address.

In some embodiments, a coronavirus testing kit includes a substrate such as with an identification code, a specimen transport container that stores a biological specimen, and a package container addressed to the respective member. Likewise, the coronavirus testing kit may also include a reply shipping container addressed to a laboratory facility or other testing facility. The reply shipping container may store the specimen transport container after a biological specimen is placed into the specimen transport container. The substrate may include a sheet of paper or other document form that includes instructions for providing a biological specimen. Furthermore, a coronavirus testing kit may be a self-test kit for at-home unsupervised administration by users, where a user may provide a saliva sample or other biological specimen to a specimen transport container. As such, coronavirus testing kits may provide rapid and accurate laboratory diagnoses for managing Covid-19 cases as well as vaccinated and/or unvaccinated populations. Users may be shown how to perform a coronavirus diagnostic test by themselves using instructions printed on a substrate (e.g., a pamphlet, brochure, or other type of insert) or a video that provides audiovisual instructions. In some embodiments, a user device may display a video in response to visiting a URL associated with an identification code

In Block 120, an identification code is provided with a coronavirus testing kit that causes a user device to describe a collection of a biological specimen in response to being scanned by a user device in accordance with one or more embodiments. In some embodiments, for example, the identification code is a quick response (QR) code that causes a user device to open a webpage in response to scanning the QR code. Example instructions for collecting a biological specimen may include how to acquire and avoid contaminating the specimen. Other instructions may describe that upon waking in the morning, the member should avoid food, water and brushing of teeth until the saliva sample is provided to the transport medium.

In Block 125, a biological specimen is sent to a laboratory facility using a specimen transport container from a coronavirus testing kit in accordance with one or more embodiments. After a user disposes a biological specimen into a return shipping container, the biological specimen may be placed within a specimen transport container inside a returning shipping container for delivery to a laboratory facility. Furthermore, the reply shipping container may include a tracking label associated with the member of the predetermined population. The tracking label be used to monitor the progress of the biological specimen in reaching a laboratory facility. For example, a postal service or other shipping service may notify the contact management server once the reply shipping container is deposited with a particular shipping entity.

Furthermore, the shipping process may include fulfillment packaging configured with one or more of the following characteristics: (a) operational and compliant for both Exempt Human Specimen and UN-3373 specimen return shipping requirements; (b) providing mailer-specific unit tracking information with respect to at-home test kit shipment status outbound and navigation communications supporting patient engagement; (c) operational and compliant with multiple tracked parcel shippers, service classes and United States Postal Service shipments, based on user selection; (d) connected, for patient-directed order intake, by user interface, API or ETL file transfer; (e) connected, by a user option, to testing labs operated or contracted by, a health system; (f) connected, by user option, to point-of-care systems such as electronic health record system; (g) connected with third-party registration systems as required; and (h) patient instructions are personalized, and contain integrated label elements that enable bar-code data capture to verify element attribution.

In Block 130, a determination is made whether a biological specimen is received at a laboratory facility for one or more members in accordance with one or more embodiments. In some embodiments, for example, a laboratory facility transmits an acknowledgement when a biological specimen is received for a particular member. If the acknowledgment is not received within a predetermined amount of time, then a server may determine that no biological specimen was received. Likewise, a contact management server may monitor tracking labels with one or more shipping services to determine whether a member has sent a return shipping container that may have the biological specimen. When a determination is made that the biological specimen from a member is received at a laboratory facility, the process may proceed to Block 150. When a determination is made that no biological specimen is received at a laboratory facility within a predetermined time period or using other criteria, the process may proceed to Block 140.

In Block 140, a notification is transmitted to a user device regarding an unreceived biological specimen in accordance with one or more embodiments. After failing to receive a biological specimen from a user, a notification may be transmitted, e.g., as a contact event executed by a contact management server. For example, some users may delay sending a biological specimen to a laboratory facility after receiving their coronavirus testing kit. Thus, various automated member outreach processes are contemplated that employ a multi-modal patient navigation communication system. In particular, different types of contact events may be used for causing members of a population to provide their biological specimens. Examples of contact events include a short message service (SMS) text message, a non-human telephone call, an email notification to a user account or user device associated with a member, a secure email message that is transmitted through a transport layer security (TLS) protocol, a message that is transmitted to an electronic health record (EHR) portal, and various messages that are transmitted to an email account using the TLS protocol and the EHR portal.

In some embodiments, contact events performed for a member are based on a predetermined priority ranking for different contact types. For more information on using different contact events to obtain a biological specimen for coronavirus diagnostic testing, see the section below titled Automated Population Outreach Systems and Methods.

In Block 150, a determination is made whether a member is positive for a coronavirus infection based on a coronavirus diagnostic test using a biological specimen in accordance with one or more embodiments. Once at a laboratory facility or other testing facility, a coronavirus diagnostic test may be performed on the biological specimen to determine whether the member is positive or negative for a coronavirus infection.

In Block 160, a notification is transmitted regarding a coronavirus infection diagnosis to a user device in accordance with one or more embodiments. After a coronavirus diagnostic test is performed on a biological specimen, a server may transmit one or more notifications based on whether a member tested positive or negative for a coronavirus infection. Accordingly, various embodiments are contemplated to manage the huge demand for administering coronavirus diagnostic tests in order to identify and control coronavirus infections throughout a population, either directly or indirectly. Thus, laboratories may use various types of medical screening assays, such as molecular assays and immunoassays, with specimen samples retrieved from transport media sent to laboratories. Indirect assays, for example, may be used detect SARS-CoV-2 infections. These indirect assays may be referred to as serological assays.

However, as some assays may produce false-negative results (e.g., due to inappropriate sample collection, to the extraction/real-time PCR workflows, to sensitivity of the particular assays used), embodiments are contemplated for management of retesting of member populations. Likewise, workflow are contemplated for managing the transport of sample specimens for different types of assays to different laboratories that may use different medical screening (e.g., due to the availability of reagents, instruments that are already in lab or acquired ad hoc). For example, processing large numbers of specimen samples within a short period may affect the normal workflow of testing laboratories, particularly during the development, evaluation, and implementation of new types of medical screening test. Thus, embodiments are contemplated to manage this SARS-CoV-2 self-testing workload.

Likewise, some embodiments are contemplated for monitoring members during verification of a particular member's contagiousness as well as post-infection. For example, a previously infected subject may be unsure about his/her protection from subsequent infections over time. In some cases, members may become positive while waiting on test results Thus, embodiments are contemplated for communicating with such members using multi-modal communication types throughout multiple phases of a SARS-CoV-2 infection (e.g., pre-infection, while waiting for a test, post-verification, post-infection, etc.).

Automated Population Outreach Systems and Methods

In general, embodiments of the disclosure include systems and methods for managing communication with members of a population. For example, the system may include a cloud-computing environment in which a user can monitor and/or manage various communication activities and contact events attributed directly with population members. In one example, a remote server may schedule and automatically transmit commands that trigger various contact events among the population members. Contact events may include different contact types, such as SMS text messages, email messages, interactive voice response (IVR) telephone calls (also called “robocalls”), live person telephone calls, messages over a social networking platform, physical letters through postal service, etc.

In some embodiments, systems and methods manage contact events for a particular outreach program. Depending on the type of outreach program, for example, different contact types may be used to achieve one or more member objectives with members of the outreach program. As such, methods and systems are contemplated that connect members using various types of user devices, such as mobile devices and mobile applications. For example, a remote server may communicate with various members over smart phones, motor vehicles, desktop computers, etc.

Turning to FIG. 2, FIG. 2 shows a block diagram of a system in accordance with one or more embodiments. As shown in FIG. 2, a contact management server (e.g., contact management server (240)) may be a remote server that includes hardware and/or software with functionality for managing and triggering various contact events (e.g., email message (231), non-human telephone call (232), telephone call by a human operator (233), and a short message service (SMS) text message (234)) regarding various user devices (e.g., user device A (211), user device B (212), user device C (213), and user device N (215)) associated with various members of a population (e.g., member A (221), member B (222), member C (223), member N (225)). Contact events may include various types of messages for notifying users, such as reminders to perform some action, seeking to obtain a desired response from a respective user. In a medical patient context, a contact event may be referred to as patient-facing “touch.” In one or more embodiments, for example, a contact event is successful where the member associated a contacted user device performs one or more tasks (e.g., providing a biological specimen for a coronavirus diagnostic test, receiving a coronavirus vaccine or vaccine booster shot) achieving the desired response to the contact event.

Keeping with FIG. 2, a contact management server may store contact information relating to various user devices (e.g., user device list B (243)) and/or members (e.g., member list A (242)) to identify recipients and other details of contact events. This contact information may include email addresses, phone numbers, website profiles (e.g., on a social networking site), user device accounts, scheduled dates for contact events, which populations a respective member is part of, contact event history, and other information relating to various contact of the respective member. User devices (e.g., user device A (211), user device B (212)) may include hardware and/or software for receiving inputs from a user and/or providing outputs to a user. Moreover, a user device may be coupled to one or more networks (e.g., network (290)), where a contact event may be performed using a user device through such a network. For example, the network may include a cellular network, a local area network or wide area network (WAN) with access to the Internet, an online platform providing a social networking service, etc. Examples of user devices may include user equipment, personal computers, smartphones, motor vehicles, smart televisions, etc.

In some embodiments, a contact management server is coupled to one or more outreach servers (e.g., outreach server (250)). An outreach server may include hardware and/or software that collects and/or analyzes data regarding population members and their user devices. For example, an outreach server may be coupled to a laboratory facility for administering a clinical outreach program. After the laboratory provides a coronavirus diagnostic test, the outreach server may receive a notification that a member completed the test.

In another embodiment, a contact management server may convey content securely between one or more secure databases e.g., databases for electronic health records located on an outreach server, and a centralized profile stored on the contact management server. Using a centralize profile, for example, a user may have dashboard visibility for member activity for a population associated with their profile.

In one or more embodiments, a contact management server is coupled to one or more application programming interfaces. For example, an application programming interface (API) may include one or more software programs that provide access to computing resources and data on servers and other computing devices. In one embodiment, the contact management server may be coupled to a third party content API (e.g., third party content API (253) disposed on web server Z (252)) that provides programmatic access to third party content, such as topical patient health education digital and video content.

As such, the third party content may be distributed to a contact management server using a cloud storage bucket. For example, a cloud storage bucket may define various types of content such as “article” content, “video” content, or “plain text” content as well segment definitions and bucket specific parameters. By using an API connection to third party content, the contact management server may integrate third party content into various outreach patient communications, such as contact events, that the contact management server manages for various populations. In one embodiment, the contact management server may have a pass-through mechanism where the third party content is transmitted to the contact management server then relayed using a contact event, such as a non-human telephone call or an email notification. In some embodiments, different types of third party content may be associated with a particular population and automatically incorporated by the contact management server into contact events.

In some embodiments, the contact management server may be use an API to couple with an electronic health record (EHR) system (e.g., electronic health records server (254)). For example, a request may be received from a user's EHR system to trigger automatically various communications, such as contact events. Likewise, upon receiving any records, such as electronic documents, of these communications, the contact management server may transmit the records to an EHR system. Thus, records obtained regarding members of a population may also be visible to users of the EHR system. The records may correspond to contact event result data and/or be a processed output using contact event result data.

Moreover, a contact management server may use multi-factor authentication to insure only authorized users view member information and/or population information. Accordingly, a contact management server, an outreach server, a web server, an electronic health records server, and user devices may be similar to a computing system (500) described below in FIGS. 5A and 5B and the accompanying description.

Accordingly, the contact management server (240) may include functionality for reporting results and/or automating follow-up contact events to non-responders of multiple populations according to different and/or overlapping member objectives.

In a medical context, a contact management server may include functionality for the following: (2) sending a member a self-test kit; (2) obtaining a sample with the self-test kit for analysis at a laboratory; (3) recording receipt of the sample and triggering processing of the results of the sample analysis; and (4) recording the success of the contact event within a respective outreach program to satisfy downstream systems measuring quality of care for the respective patient and/or a population within the respective outreach program.

In one or more embodiments, the contact management server (240) includes functionality for administering various processes for systematically defining and automating a series of contact events with a particular member. In response to detecting that a member has not performed a requested activity under a member objective, e.g., no sample from a self-testing kit has been received or analyzed by a laboratory, the contact management server (240) may automatically schedule another contact event that is the same contact type or of a different contact type for the member.

While FIG. 2 shows various configurations of components, other configurations may be used without departing from the scope of the disclosure. For example, various components in FIG. 2 may be combined to create a single component. As another example, the functionality performed by a single component may be performed by two or more components.

Turning to FIG. 3, FIG. 3 shows a flowchart in accordance with one or more embodiments. Specifically, FIG. 3 describes a general method for managing contact events for a user device. One or more blocks in FIG. 3 may be performed by one or more components (e.g., contact management server (240)) as described in FIGS. 2, 5A, 5B, 6A, 6B, and 7. While the various blocks in FIG. 3 are presented and described sequentially, one of ordinary skill in the art will appreciate that some or all of the blocks may be executed in different orders, may be combined or omitted, and some or all of the blocks may be executed in parallel. Furthermore, the blocks may be performed actively or passively.

In Block 300, a request to trigger a contact event of a user device is obtained in accordance with one or more embodiments. For example, a user may access over the Internet a centralized profile on a remote server with various contact event settings. The centralized profile may manage contact events for various members in a particular population that the user is granted privileges for managing. As such, the user may individually send requests to the contact management server to adjust contact event settings regarding scheduled dates/times and parameters for automatically transmitting commands to trigger contact events.

In some embodiments, the contact management server performs an algorithm, such as a machine learning algorithm, to determine which contact types have the highest degree of success for a particular member or population. Likewise, the remote server may automatically send a request to perform a contact event based on comparing one or more population profiles with an incumbent profile. Based on the degrees of contact event effectiveness for different contact event settings, a remote sever can automate the process.

In Block 310, one or more previous contact events of a user device are determined in accordance with one or more embodiments. For example, user devices may be contacted using multi-modal communication capabilities for multiple contact types: print/mail, email, SMS text, non-human telephone calls based on interactive voice responses (“robocalls”), telephone calls with human operators, communication services provides by mobile devices and/or mobile applications, etc. A server may analyze previous types of contact events, such as to identify whether a previous contact event should be repeated or a different contact event should be attempted for the user device. Previous contact events may be stored in a database that records contact event history for user devices and/or members.

In Block 320, a priority ranking of various contact types is obtained in accordance with one or more embodiments. In one embodiment, different contact types have static rankings that determine the order that certain types are triggered for contacting a user device. In some embodiments, the priority ranking is based on one or more characteristics of a population. Likewise, contact types in a priority ranking may be manually selected by a user with a centralized profile or automatically determined using one or more algorithms and contact event results from the respective population or similar populations. In some embodiments, the priority ranking is adjusted based on contact event result data.

In Block 330, a selection of a contact type for contacting a user device is determined based on one or more previous contact events in accordance with one or more embodiments. For example, based on a particular outreach program, a server may initiate contact of a member with a default contact event, such as a phone text message or a non-human telephone call. Depending on whether a response is detected for any previous contact events, the same contact event or a different contact event may be selected. For example, where a priority ranking is used to manage contact events, a server may automatically select a particular contact type for a specific number of times. After performing the contact type a specific number of times, a server may change to a different contact type according to the priority ranking. Thus, an iterative process may be performed to select and/or exclude particular contact types for use in managing a population.

In Block 340, a command is transmitted that triggers a contact event of a user device based on a selection of a contact type in accordance with one or more embodiments. For example, a server may have one or more applications that have computer telephony integration, e.g., to generate an interactive voice response in a non-human telephone call. Here, a computer device may interact with members through the use of voice and dual-tone multi-frequency signaling (DTMF) tones input via a keypad. In some embodiments, telephony application programming interface (TAPI) may provide such computer telephony integration and enable a computer device to use telephone services. Thus, a server may perform a contact event or transmit a message to a different computer device to perform the contact event. Likewise, the contact event may result in an interaction between a server and a member via a telephone keypad or by speech recognition.

Turning to FIG. 4, FIG. 4 shows a flowchart in accordance with one or more embodiments. Specifically, FIG. 4 describes a general method for managing contact events for multiple user devices associated with a particular population. One or more blocks in FIG. 4 may be performed by one or more components (e.g., contact management server (240)) as described in FIGS. 2, 5A, 5B, 6A, 6B, and 7. While the various blocks in FIG. 4 are presented and described sequentially, one of ordinary skill in the art will appreciate that some or all of the blocks may be executed in different orders, may be combined or omitted, and some or all of the blocks may be executed in parallel. Furthermore, the blocks may be performed actively or passively.

In Block 400, contact event result data is obtained regarding various user devices in accordance with one or more embodiments. In some embodiments, a server may provide a standard point of intake for incoming data from one or more outreach servers. Thus, contact event result data may be aggregated, e.g., at a contact management server for performing an analysis and/or comparisons. In particular, contact event result data may include information that indicates whether a member objective was achieved in response to one or more contact events. Likewise, the contact event result data may indicate whether no success has occurred by a member following the contact event.

In Block 410, a subset of previous contact events are determined based on contact event result data that failed to result in members satisfying a predetermined member objective in accordance with one or more embodiments. For example, a server may analyze contact event result data to determine one or more subsets of contact events that satisfied or fails to achieve a member objective. A member subset that satisfied the predetermined member objective may be removed from the contact sequence, while members subsets that failed to satisfy the predetermined member objective may receive future contact events seeking a response accordingly.

In some embodiments, the member objective may be binary, e.g., a patient delivered a medical test sample to a laboratory or failed to deliver the biological specimen. In other embodiments, the member objective may be scored using various attributes, e.g., how fast after a contact event was performed did the patient deliver the sample or how many times did the patient visitor a doctor within a predetermined time period. In some embodiments, the member objective is determined dynamically according to an algorithm, e.g., based on a machine learning model that optimizes contact sequences for a particular member or multiple members of a population.

In Block 420, a contact type is determined that is different from one or more contact types associated with one or more previous contact events in accordance with one or more embodiments. For example, if a previous contact event fails to cause a member to produce a desired response, a different contact type may be used in hope of achieving a different result. In some embodiments, a server may analyze contact event result data for one or more populations in order to optimize contact event performance. Thus, different contact types may be applied to a population's members in order to increase the contact event success rate.

In Block 430, one or more commands are transmitted that trigger one or more contact events based on a determined contact type in accordance with one or more embodiments. Block 430 may be performed in a similar manner as described above in Block 340 and the accompanying description.

Computing System

Embodiments may be implemented on a computing system. Any combination of mobile, desktop, server, router, switch, embedded device, or other types of hardware may be used. For example, as shown in FIG. 5A, the computing system (500) may include one or more computer processors (502), non-persistent storage (504) (e.g., volatile memory, such as random access memory (RAM), cache memory), persistent storage (506) (e.g., a hard disk, an optical drive such as a compact disk (CD) drive or digital versatile disk (DVD) drive, a flash memory, etc.), a communication interface (512) (e.g., Bluetooth interface, infrared interface, network interface, optical interface, etc.), and numerous other elements and functionalities.

The computer processor(s) (502) may be an integrated circuit for processing instructions. For example, the computer processor(s) may be one or more cores or micro-cores of a processor. The computing system (500) may also include one or more input devices (510), such as a touchscreen, keyboard, mouse, microphone, touchpad, electronic pen, or any other type of input device.

The communication interface (512) may include an integrated circuit for connecting the computing system (500) to a network (not shown) (e.g., a local area network (LAN), a wide area network (WAN) such as the Internet, mobile network, or any other type of network) and/or to another device, such as another computing device.

Further, the computing system (500) may include one or more output devices (508), such as a screen (e.g., a liquid crystal display (LCD), a plasma display, touchscreen, cathode ray tube (CRT) monitor, projector, or other display device), a printer, external storage, or any other output device. One or more of the output devices may be the same or different from the input device(s). The input and output device(s) may be locally or remotely connected to the computer processor(s) (502), non-persistent storage (504), and persistent storage (506). Many different types of computing systems exist, and the aforementioned input and output device(s) may take other forms.

Software instructions in the form of computer readable program code to perform embodiments of the disclosure may be stored, in whole or in part, temporarily or permanently, on a non-transitory computer readable medium such as a CD, DVD, storage device, a diskette, a tape, flash memory, physical memory, or any other computer readable storage medium. Specifically, the software instructions may correspond to computer readable program code that, when executed by a processor(s), is configured to perform one or more embodiments of the disclosure.

The computing system (500) in FIG. 5A may be connected to or be a part of a network. For example, as shown in FIG. 5B, the network (520) may include multiple nodes (e.g., node X (522), node Y (524)). Each node may correspond to a computing system, such as the computing system shown in FIG. 5A, or a group of nodes combined may correspond to the computing system shown in FIG. 5A. By way of an example, embodiments of the disclosure may be implemented on a node of a distributed system that is connected to other nodes. By way of another example, embodiments of the disclosure may be implemented on a distributed computing system having multiple nodes, where each portion of the disclosure may be located on a different node within the distributed computing system. Further, one or more elements of the aforementioned computing system (500) may be located at a remote location and connected to the other elements over a network.

Although not shown in FIG. 5B, the node may correspond to a blade in a server chassis that is connected to other nodes via a backplane. By way of another example, the node may correspond to a server in a data center. By way of another example, the node may correspond to a computer processor or micro-core of a computer processor with shared memory and/or resources.

The nodes (e.g., node X (522), node Y (524)) in the network (520) may be configured to provide services for a client device (526). For example, the nodes may be part of a cloud computing system. The nodes may include functionality to receive requests from the client device (526) and transmit responses to the client device (526). The client device (526) may be a computing system, such as the computing system shown in FIG. 5A. Further, the client device (526) may include and/or perform all or a portion of one or more embodiments of the disclosure.

The computing system or group of computing systems described in FIGS. 5A and 5B may include functionality to perform a variety of operations disclosed herein. For example, the computing system(s) may perform communication between processes on the same or different systems. A variety of mechanisms, employing some form of active or passive communication, may facilitate the exchange of data between processes on the same device. Examples representative of these inter-process communications include, but are not limited to, the implementation of a file, a signal, a socket, a message queue, a pipeline, a semaphore, shared memory, message passing, and a memory-mapped file. Further details pertaining to a couple of these non-limiting examples are provided below.

Based on the client-server networking model, sockets may serve as interfaces or communication channel end-points enabling bidirectional data transfer between processes on the same device. Foremost, following the client-server networking model, a server process (e.g., a process that provides data) may create a first socket object. Next, the server process binds the first socket object, thereby associating the first socket object with a unique name and/or address. After creating and binding the first socket object, the server process then waits and listens for incoming connection requests from one or more client processes (e.g., processes that seek data). At this point, when a client process wishes to obtain data from a server process, the client process starts by creating a second socket object. The client process then proceeds to generate a connection request that includes at least the second socket object and the unique name and/or address associated with the first socket object. The client process then transmits the connection request to the server process. Depending on availability, the server process may accept the connection request, establishing a communication channel with the client process, or the server process, busy in handling other operations, may queue the connection request in a buffer until the server process is ready. An established connection informs the client process that communications may commence. In response, the client process may generate a data request specifying the data that the client process wishes to obtain. The data request is subsequently transmitted to the server process. Upon receiving the data request, the server process analyzes the request and gathers the requested data. Finally, the server process then generates a reply including at least the requested data and transmits the reply to the client process. The data may be transferred, more commonly, as datagrams or a stream of characters (e.g., bytes).

Shared memory refers to the allocation of virtual memory space in order to substantiate a mechanism for which data may be communicated and/or accessed by multiple processes. In implementing shared memory, an initializing process first creates a shareable segment in persistent or non-persistent storage. Post creation, the initializing process then mounts the shareable segment, subsequently mapping the shareable segment into the address space associated with the initializing process. Following the mounting, the initializing process proceeds to identify and grant access permission to one or more authorized processes that may also write and read data to and from the shareable segment. Changes made to the data in the shareable segment by one process may immediately affect other processes, which are also linked to the shareable segment. Further, when one of the authorized processes accesses the shareable segment, the shareable segment maps to the address space of that authorized process. Often, one authorized process may mount the shareable segment, other than the initializing process, at any given time.

Other techniques may be used to share data, such as the various data described in the present application, between processes without departing from the scope of the disclosure. The processes may be part of the same or different application and may execute on the same or different computing system.

Rather than or in addition to sharing data between processes, the computing system performing one or more embodiments of the disclosure may include functionality to receive data from a user. For example, in one or more embodiments, a user may submit data via a graphical user interface (GUI) on the user device. Data may be submitted via the graphical user interface by a user selecting one or more graphical user interface widgets or inserting text and other data into graphical user interface widgets using a touchpad, a keyboard, a mouse, or any other input device. In response to selecting a particular item, information regarding the particular item may be obtained from persistent or non-persistent storage by the computer processor. Upon selection of the item by the user, the contents of the obtained data regarding the particular item may be displayed on the user device in response to the user's selection.

By way of another example, a request to obtain data regarding the particular item may be sent to a server operatively connected to the user device through a network. For example, the user may select a uniform resource locator (URL) link within a web client of the user device, thereby initiating a Hypertext Transfer Protocol (HTTP) or other protocol request being sent to the network host associated with the URL. In response to the request, the server may extract the data regarding the particular selected item and send the data to the device that initiated the request. Once the user device has received the data regarding the particular item, the contents of the received data regarding the particular item may be displayed on the user device in response to the user's selection. Further to the above example, the data received from the server after selecting the URL link may provide a web page in Hyper Text Markup Language (HTML) that may be rendered by the web client and displayed on the user device.

Once data is obtained, such as by using techniques described above or from storage, the computing system, in performing one or more embodiments of the disclosure, may extract one or more data items from the obtained data. For example, the extraction may be performed as follows by the computing system (500) in FIG. 5A. First, the organizing pattern (e.g., grammar, schema, layout) of the data is determined, which may be based on one or more of the following: position (e.g., bit or column position, Nth token in a data stream, etc.), attribute (where the attribute is associated with one or more values), or a hierarchical/tree structure (consisting of layers of nodes at different levels of detail—such as in nested packet headers or nested document sections). Then, the raw, unprocessed stream of data symbols is parsed, in the context of the organizing pattern, into a stream (or layered structure) of tokens (where each token may have an associated token “type”).

Next, extraction criteria are used to extract one or more data items from the token stream or structure, where the extraction criteria are processed according to the organizing pattern to extract one or more tokens (or nodes from a layered structure). For position-based data, the token(s) at the position(s) identified by the extraction criteria are extracted. For attribute/value-based data, the token(s) and/or node(s) associated with the attribute(s) satisfying the extraction criteria are extracted. For hierarchical/layered data, the token(s) associated with the node(s) matching the extraction criteria are extracted. The extraction criteria may be as simple as an identifier string or may be a query presented to a structured data repository (where the data repository may be organized according to a database schema or data format, such as XML).

The extracted data may be used for further processing by the computing system. For example, the computing system of FIG. 5A, while performing one or more embodiments of the disclosure, may perform data comparison. Data comparison may be used to compare two or more data values (e.g., A, B). For example, one or more embodiments may determine whether A>B, A=B, A!=B, A<B, etc. The comparison may be performed by submitting A, B, and an opcode specifying an operation related to the comparison into an arithmetic logic unit (ALU) (i.e., circuitry that performs arithmetic and/or bitwise logical operations on the two data values). The ALU outputs the numerical result of the operation and/or one or more status flags related to the numerical result. For example, the status flags may indicate whether the numerical result is a positive number, a negative number, zero, etc. By selecting the proper opcode and then reading the numerical results and/or status flags, the comparison may be executed. For example, in order to determine if A>B, B may be subtracted from A (i.e., A−B), and the status flags may be read to determine if the result is positive (i.e., if A>B, then A−B>0). In one or more embodiments, B may be considered a threshold, and A is deemed to satisfy the threshold if A=B or if A>B, as determined using the ALU. In one or more embodiments of the disclosure, A and B may be vectors, and comparing A with B includes comparing the first element of vector A with the first element of vector B, the second element of vector A with the second element of vector B, etc. In one or more embodiments, if A and B are strings, the binary values of the strings may be compared.

The computing system in FIG. 5A may implement and/or be connected to a data repository. For example, one type of data repository is a database. A database is a collection of information configured for ease of data retrieval, modification, re-organization, and deletion. Database Management System (DBMS) is a software application that provides an interface for users to define, create, query, update, or administer databases.

The user, or software application, may submit a statement or query into the DBMS. Then the DBMS interprets the statement. The statement may be a select statement to request information, update statement, create statement, delete statement, etc. Moreover, the statement may include parameters that specify data, or data container (database, table, record, column, view, etc.), identifier(s), conditions (comparison operators), functions (e.g. join, full join, count, average, etc.), sort (e.g. ascending, descending), or others. The DBMS may execute the statement. For example, the DBMS may access a memory buffer, a reference or index a file for read, write, deletion, or any combination thereof, for responding to the statement. The DBMS may load the data from persistent or non-persistent storage and perform computations to respond to the query. The DBMS may return the result(s) to the user or software application.

The computing system of FIG. 5A may include functionality to present raw and/or processed data, such as results of comparisons and other processing. For example, presenting data may be accomplished through various presenting methods. Specifically, data may be presented through a user interface provided by a computing device. The user interface may include a GUI that displays information on a display device, such as a computer monitor or a touchscreen on a handheld computer device. The GUI may include various GUI widgets that organize what data is shown as well as how data is presented to a user. Furthermore, the GUI may present data directly to the user, e.g., data presented as actual data values through text, or rendered by the computing device into a visual representation of the data, such as through visualizing a data model.

For example, a GUI may first obtain a notification from a software application requesting that a particular data object be presented within the GUI. Next, the GUI may determine a data object type associated with the particular data object, e.g., by obtaining data from a data attribute within the data object that identifies the data object type. Then, the GUI may determine any rules designated for displaying that data object type, e.g., rules specified by a software framework for a data object class or according to any local parameters defined by the GUI for presenting that data object type. Finally, the GUI may obtain data values from the particular data object and render a visual representation of the data values within a display device according to the designated rules for that data object type.

Data may also be presented through various audio methods. In particular, data may be rendered into an audio format and presented as sound through one or more speakers operably connected to a computing device.

Data may also be presented to a user through haptic methods. For example, haptic methods may include vibrations or other physical signals generated by the computing system. For example, data may be presented to a user using a vibration generated by a handheld computer device with a predefined duration and intensity of the vibration to communicate the data.

The above description of functions presents only a few examples of functions performed by the computing system of FIG. 5A and the nodes and/or client device in FIG. 5B. Other functions may be performed using one or more embodiments of the disclosure.

Transportation Devices and Systems for Medical Screening Assays

In some embodiments, a coronavirus testing kit may include a package container for delivery to a member's household or other address. For example, a package container may be a package envelope or other container for shipping one or more items (i.e., shipping items) from a source to a destination. The destination of the package container may be identified by a shipping address, where the shipping address may be printed directly on the package container, or may be placed inside the package container and made viewable from the exterior of the package container by replacing a portion of the package container with a transparent material (e.g., plastic). In contrast, the source or origin of the package container may be identified by a return address. Like the shipping address, the return address may be printed directly on the package container.

In one or more embodiments, a coronavirus testing kit includes a specimen-holding receptacle (SHR) for collecting and storing a biological specimen. The specimen-holding receptacle may be separate from the specimen transport container. For example, the specimen-holding receptacle may be a tube that includes a buffer agent (e.g., for stabilizing or inactivating a coronavirus agent), while the specimen transport container is a protective housing or biological hazard bag for protecting the tube.

Turning to FIGS. 6A and 6B, FIGS. 6A and 6B show an example in accordance with one or more embodiments. As shown in FIG. 6A, a coronavirus testing kit (600) includes a substrate (601) that includes an identification code (602), a specimen transport container (603), a reply shipping container (611), and a package container (609). Once the package container (609) is received by the patient, the specimen transport container (603) may be removed from the package container (609) and shipped to the laboratory testing facility. In FIG. 6B, a specimen transport container may include a biohazard bag (607) that includes an SHR (605).

Automated Data Integration for Various Contact Types

Turning to FIG. 7, FIG. 7 provides an example of a contact management workflow in accordance with one or more embodiments. The following example is for explanatory purposes only and not intended to limit the scope of the disclosed technology. In FIG. 7, after an electronic visit (701), a population managing organization (710) uses a member list generator (711) to generate a member list (715) of a predetermined population. The member list (715) may be transmitted to a member list intake (721) for a contact management organization (720), e.g., that provides an API for member lists. Likewise, the member list (715) may also be transmitted to a member data store (712). At the member data store (712), the member list (715) may be used with a pop network protocol to transmit member data (716) to a contact management server (723) hosted by a contact management organization (720) and through an application programming interface (API) (725). For example, the member list (715) and the member data (716) may be used by the contact management server (723) to perform contact events regarding a particular population include member (730).

Keeping with the contact management organization (720) in FIG. 7, the member list intake (721) may transmit the member list (715) to a member objective fulfillment monitor (722) that is responsible for delivering self-test kits (e.g., self-test kit (726)) to population members (e.g., member (730)). According the member objective fulfillment monitor (722) may notify the contact management server (723) when a self-test kit is initially sent to member (730) as well as providing tracking information to the contact management server (723) regarding the package. In Block 731 of FIG. 7, the member (730) receives the self-test kit and proceeds to access a registration website, i.e., test attribution server (751) operated by the test provider (750). The test attribution server (751) may then notify the contact management server (723) of the registration of member (730) through the API (725). Returning to member (730), the member (730) may complete the self-test kit in Block 732 and return the completed self-test kit in Block 733. Thus, the completed self-test kit (736) may be shipped to laboratory (741) that is operated by the laboratory organization (740). Once the laboratory server (742) obtains the laboratory results (745) from the laboratory (741), the laboratory results (745) may be transmitted to the population managing organization (710) to form a portion of a contact event summary (713). In some embodiments, the laboratory results (745) may be transmitted to the contact management server (723), but will not in many cases based on privacy compliance regulations.

In some embodiments, contact types include secure email, facsimile (fax) transmissions, and other document transmissions. For example, a contact event may include transmitting third party content using one or more contact types described through this disclosure. Likewise, some embodiments include integration with third party content APIs, such as to provide contact event status updates and test kit registration data. Some embodiments have automated data integration between contact management servers and laboratories and electronic health record (EHR) systems. Likewise, some embodiments include user controls that provide users with the functionality to specifically administer patient contact management workflows over time.

In some embodiments, a contact event corresponds to a secure end-to-end messaging of members in a particular population. For example, a contact management server may trigger contact events based on secure communication protocols. Thus, member security may be implemented, while also optimizing a member's experience and removing impediments to engagement with various entities in the contact management workflow. In particular, members may not want to login into a secure site, such as an EHS portal provided by an EHS portal server, in order to view content or read messages. In other words, members may want to limit their communication to their existing methods of communication. Accordingly, a contact event may be secure and compliant with various privacy laws. Thus, some embodiments are contemplated that allow for portal-style access to view secure emails in addition to transport layer security (TLS) delivery options. In some embodiments, a member or a population managing organization may be able to determine whether individual contact events will include TLS-only events, TLS events and/or portal events, or portal-only events. Accordingly, users may be able to use a custom authentication challenge when using the portal, such as knowledge factors that include (Enter medical record number (MRN), date of birth (DOB), etc.)

In some embodiments, contact events include prescriber facsimile (fax) bursts to one or more facsimile machines. For example, a contact management server may perform an automated workflow that implements a fax burst event in response to a user request. A fax burst may include consistent and on-going fax messages. Thus, a fax contact event may be an available option within a user interface or a core system.

In some embodiments, contact events are integrated directly with EHR servers and laboratory servers. For example, various EHR systems and lab providers in order to send and receive data directly when appropriate. For example, rather than transferring data via a flat file that involves import/exports by different entities, a contact management server may be able obtain and transmit data while being blind to updates in an EHR system. Some embodiments may use a third-party provider for EHR/lab connectivity, where API interfaces are used with a the third-party provider. In some embodiments, push points are used to transmit data into the EHR systems and/or laboratory systems. Furthermore, some embodiments include using pull points for transmitting data from EHR systems and/or laboratory systems. Thus, direct data queries may be performed with respect to EHR systems or laboratory systems.

In some embodiments, branching workflow paths and member list adjustments are performed during a contact management workflow. For example, member lists may be adjusted based along with contact sequences for individual members and/or populations. In particular, members may have changes that make them no longer relevant to a particular workflow, e.g., a patient receiving medical treatment joins a different healthcare provider from the population management organization using the contact management workflow. Likewise, a workflow may require more nuances than batch processing may provide, and thus some embodiments may handle each member as an individual element within the workflow. Without doing so, members may continue to receive irrelevant communications or could miss out on a direct connection with a population managing organization.

Some embodiments include a single-entity processing through workflow, where each member is a single entity that allows them to move to experience a contact sequence of events tailored for them individually. A single-entity workflow may branch into separate paths based on applying logic to contact result data, for example. Thus, a member may have the ability to branch the single-entity workflow into separate paths based on activities that occur along the way, such as laboratory results.

In some embodiments, end users may search for content and generate special contact events using third party content dynamically, as well as other dynamic content creation tools. Accordingly, a population managing organization may transmit a request to a contact management server to adjust message content and/or format. Thus, third party content API Integration may provide the functionality to search for desired content desired as well as insert desired contact in contact event messages. In some embodiments, a contact management server may provide the ability to generate and/or adjust content in a graphical user interface editor (such as a central dashboard) using one or more generic templates.

Likewise, some embodiments include the ability to modify member data, such as manually through a user interface or through one or more automation processes, such as by connecting a member data store to an API.

Some embodiments include virtual physician oversight. For example, some health systems may have their own captive process for cycling needed at-home test fulfillment through a physician's review process so that any resulting order (e.g., provided to a contact management server) that is receive has associated with it a physician's order, a standing lab order and the associated coding required in front line systems like the electronic health record. In some embodiments, one or more servers may support orders by prospective clients (e.g., accountable care organizations, insurance payers, employer groups) that may not have the capability to support such a system. Thus, some embodiments automate a workflow (e.g., using an API) such that a population managing organization's system may transmit a list of candidate recipients for test fulfillment. The list of candidate recipients may be passed to a virtual telehealth provider who then reviews and approves/declines the order, thereby providing (upon approval) the back-end transaction specifics for proceeding with a fulfillment (e.g., a pharmacy, lab order, physician provider ID, etc.).

Moreover, embodiments using virtual physician oversight may include one or more of the following: (1) non-integrated health Plans may require process to review target population list and issue lab orders for lab tests; (2) once candidate target population list is uploaded, it may be passed to virtual health provider; (3) connect to API for data exchange, both inbound and outbound HL7 (or other data formats); (4) physician review may occur and issuance of lab request orders (e.g., data transactions and associated PDFs of physician orders); (5) process may pass the target list to a virtual health provider for lab orders; return scripts and documents come back to a navigation tool; (6) any patients for whom screening was declined may be routed back to a plan for action; (7) a contact management server may store an archive of lab requests and results; (8) plans accessing may only have access to that plan's member data; (9) archival documents may be selected for export to remote EHR using API tool for this process; and (10) data may be online for 3 years +current YTD, archived for 10 years, or longer as required by user systems.

Some embodiments include live call integration. In addition to text-to-voice IVR call automation capability, for example, some embodiments may provide the capability to route a task list or workflow queue for live agent contact with members (e.g., patients) on behalf of a population managing organization's systems. The providers of the actual calls may be any combination of professional call centers, virtualized clinical support staff resources, or a UI enabling the population managing organization's system themselves to access servers to drive call center queues and record outcomes, log and/or close events.

Furthermore, some embodiments provide data integration between various entities. For example, a virtual health/telehealth entity (e.g., through an API) may have an API that handles outbound candidate target population lists for coronavirus diagnostic tests and inbound physician lab order (or not)—transactions and PDF artifacts and lab test results/dates. In another embodiment, an email entity's API may have outbound email lists (with template IDs, by client, by outreach) and inbound send/receive/open/bounce results, dates, and/or times. In another embodiment, IVR/robocalls entity have provide an API that handles outbound call lists (e.g., with script IDs, by client, by outreach) and inbound call log results, dates, and/or times. In another embodiment, an EHR connectivity entity may have an API that integrates outbound PDF and other document artifacts documenting patient outreach touches per entity rules. In another embodiment, SMS text entity may have an API that integrates outbound text msg lists (e.g., with template IDs, by client, by outreach) and inbound send/receive/open/bounce results, dates, and/or times. Finally, in another embodiment, a live call entity may use secure File transfer protocol (sFTP) ETL batch files for integrating outbound call lists (e.g., with script IDs, by client, by outreach), enabling clinical staff to initiate calls to members, and/or inbound call log results, dates, and/or times. ETL is a type of data integration that refers to the three steps (i.e., “ETL” refers to “extract, transform, load”) used to blend data from multiple sources.

In some embodiments, live call integration may use sFTP transmission of a batch of live calls queued for action to provider vendor, identifying client Plan, member call information and script to be executed. In another embodiment, live call integration may use a vendor-facing web page through which backlog lists of patients/members queued up for live follow-up calls would be presented for action.

Some embodiments may include EHR integration. For example, EHR integration may include one or more of the following: (1) connector APIs can enable access that can homogenize the connection to almost all industry EHRs; (2) if used, applicable fulfillment archival PDFs will be transmitted to target provide EHR/patient chart for frontline access; (3) a contact management server may store an archive of what got transmitted to EHR; (4) plans accessing must only have access to that Plan's member data; (5) archival documents may be selected for export to remote EHR using API tool for this process; (6) data may be online for 3 years+current YTD, archived for 10 years; and (7) two way transmissions may be possible.

Although only a few example embodiments have been described in detail above, those skilled in the art will readily appreciate that many modifications are possible in the example embodiments without materially departing from this invention. Accordingly, all such modifications are intended to be included within the scope of this disclosure as defined in any filed claims. In the claims, any means-plus-function clauses are intended to cover the structures described herein as performing the recited function(s) and equivalents of those structures. Similarly, any step-plus-function clauses in the claims are intended to cover the acts described here as performing the recited function(s) and equivalents of those acts. It is the express intention of the applicant not to invoke 35 U.S.C. § 112(f) for any limitations of any of the claims herein, except for those in which the claim expressly uses the words “means for” or “step for” together with an associated function. 

What is claimed is:
 1. A method, comprising: determining, by a server, whether to perform a first coronavirus diagnostic test on a first member of a predetermined population; sending, by the server in response to determining that the first coronavirus diagnostic test should be performed on the first member, a coronavirus testing kit to the first member, wherein the coronavirus testing kit comprises a return shipping container, a substrate comprising an identification code, and a first specimen transport container configured to store a biological specimen, and wherein the identification code causes a first user device to describe a performance of the first coronavirus diagnostic test to acquire the biological specimen in response to being scanned by the first user device; determining, by the server, whether the biological specimen is received at a laboratory facility from the first member; and transmitting, by the server and to at least one user device associated with the first member, a notification regarding a coronavirus infection diagnosis based on the biological specimen in response to the biological specimen being received at the laboratory facility.
 2. The method of claim 1, further comprising: transmitting, by the server and to a second user device associated with a second member of the predetermined population, a second notification regarding a second biological specimen not being received in response to receiving no receipt acknowledgement of a second specimen transport container within a predetermined amount of time.
 3. The method of claim 1, wherein the biological specimen is a saliva sample from the first member.
 4. The method of claim 1, further comprising: determining, by the server, that the first member tested negative for a coronavirus infection; and transmitting, by the server, a plurality of notifications to a plurality of user devices associated with a plurality of members of the predetermined population regarding a negative coronavirus test in response to determining that the first member tested negative.
 5. The method of claim 1, further comprising: determining, by the server, whether the first member has received a coronavirus vaccine, wherein the first coronavirus diagnostic test is determined to be performed on the first member based on the first member not receiving the coronavirus vaccine.
 6. The method of claim 1, wherein determining whether to perform the first coronavirus diagnostic test on the first member comprises determining whether the first member was within a predetermined proximity to a second member of the predetermined population that is diagnosed as being positive with a coronavirus infection.
 7. The method of claim 1, wherein the identification code is a quick response (QR) code.
 8. The method of claim 1, further comprising: determining, by the server, a contact sequence for contacting a second user device, wherein the second user device is associated with a second member of the predetermined population; determining, by the server and within the contact sequence, a previous contact event of the second user device, wherein the previous contact event corresponds to a request of the second member to send a second biological specimen regarding a second coronavirus testing kit; determining, by the server, a selection of a first contact type for contacting the second user device, wherein the first contact type is different from a second contract type associated with the previous contact event; and transmitting, by the server, a command that triggers a contact event of the second user device based on the selection of the first contact type.
 9. The method of claim 1, further comprising: determining, by the server, a predetermined priority ranking for a plurality of different contact types, wherein the predetermined priority ranking determines an order that the plurality of different contact types are used for contacting one or more members of the predetermined population, and wherein the plurality of different contact types comprises a short message service (SMS) text message, a non-human telephone call, and an email notification.
 10. The method of claim 9, wherein the plurality of different contact types comprises: a secure email message that is transmitted through a transport layer security (TLS) protocol; a message that is transmitted to an electronic health record (EHR) portal; and a plurality of messages that are transmitted to an email account using the TLS protocol and the EHR portal.
 11. The method of claim 1, further comprising: obtaining, by the server and from an electronic health record (EHR) portal server, contact information regarding the first member, and wherein the first coronavirus diagnostic test is sent to the first member using the contact information.
 12. A system, comprising: a plurality of user devices coupled to a network, wherein each user device is associated with a respective member of a predetermined population; a contact management server coupled to the network, and wherein the contact management server is configured to: determine whether to perform a first coronavirus diagnostic test on a first member of the predetermined population; send, in response to determining that the first coronavirus diagnostic test should be performed on the first member, a coronavirus testing kit to the first member, wherein the coronavirus testing kit comprises a return shipping container, a substrate comprising an identification code, and a first specimen transport container configured to store a biological specimen, and wherein the identification code causes a first user device among the plurality of user devices to describe a performance of the first coronavirus diagnostic test to acquire the biological specimen in response to being scanned by the first user device; determine whether the biological specimen is received at a laboratory facility from the first member; and transmit, to at least one user device among the plurality of user devices, a notification regarding a coronavirus infection diagnosis based on the biological specimen in response to the biological specimen being received at the laboratory facility.
 13. The system of claim 12, wherein the contact management server is further configured to: transmitting, to a second user device associated with a second member of the predetermined population, a second notification regarding a second biological specimen not being received in response to receiving no receipt acknowledgement of a second specimen transport container within a predetermined amount of time.
 14. The system of claim 12, wherein the biological specimen is a saliva sample from the first member.
 15. The system of claim 12, wherein the contact management server is further configured to: determine that the first member tested negative for a coronavirus infection; and transmit a plurality of notifications to a plurality of user devices associated with a plurality of members of the predetermined population regarding a negative coronavirus test in response to determining that the first member tested negative.
 16. The system of claim 12, wherein the contact management server is further configured to: determine whether the first member has received a coronavirus vaccine, wherein the first coronavirus diagnostic test is determined to be performed on the first member based on the first member not receiving the coronavirus vaccine.
 17. The system of claim 12, wherein determining whether to perform the first coronavirus diagnostic test on the first member comprises determining whether the first member was within a predetermined proximity to a second member of the predetermined population that is diagnosed as being positive with a coronavirus infection.
 18. An apparatus, comprising: a substrate comprising an identification code; a specimen transport container configured to store a biological specimen; and a package container addressed to a member of a predetermined population, the package container comprising: a reply shipping container addressed to a laboratory facility and configured to store the specimen transport container after a biological specimen is placed into the specimen transport container, wherein the reply shipping container comprises a tracking label associated with the member of the predetermined population, wherein the tracking label is configured to notify a server that the biological specimen is received by the laboratory facility, and wherein the identification code causes a user device to describe a performance of a coronavirus diagnostic test to acquire the biological specimen in response to being scanned by the user device.
 19. The apparatus of claim 18, wherein the biological specimen is a saliva sample from the member.
 20. The apparatus of claim 18, wherein the identification code is a quick response (QR) code. 